BBS Toolkit

home *** CD-ROM | disk | FTP | other *** search

/ BBS Toolkit / BBS Toolkit.iso / programs / vbbs542.zip / NETGUIDE.DOC < prev next >

Wrap

Text File | 1992-02-12 | 44KB | 953 lines

▒▒▄ ▒▒▄ ▒▒▄ ▒▒▒▒▒▒▄ ▒▒▒▒▒▒▄ ▒▒▄ ▒▒▄ ▒▒▒▒▒▒▄ ▒▒▄ ▒▒█ ▒▒█ ▒▒█ ▒▒█▀▒▒█ ▀▒▒█▀▀ ▒▒█ ▒▒█ ▒▒█▀▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒▒▒▒█▀ ▒▒█ ▒▒█ ▒▒█ ▒▒▒▒▒▒█ ▒▒█ ▒▒▒▒█▀ ▒▒█ ▒▒█▀▒▒▄ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒█▀ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒▒▒▒▒█ ▒▒█ ▒▒█ ▒▒▒▒▒▒▄ ▀▀ ▀▀ ▀▀ ▀▀ ▀▀ ▀▀▀▀▀▀ ▀▀ ▀▀ ▀▀▀▀▀▀ ▒▒▒▄▄ ▒▒▄ ▒▒▒▒▒▒▄ ▒▒▒▒▒▒▄ ▒▒█▒▒█▒▒█ ▒▒█▀▀▀▀ ▀▒▒█▀▀ ▒▒█ ▀▒▒▒█ ▒▒▒▒▒▄ ▒▒█ ▒▒█ ▒▒█ ▒▒█▀▀▀ ▒▒█ ▒▒█ ▒▒█ ▒▒▒▒▒▒▄ ▒▒█ ▀▀ ▀▀ ▀▀▀▀▀▀ ▀▀ The VirtualNET Guide ───────────────────────────────────────────────────────── - Table of Contents - About VirtualNET............................. 1 Network Message Areas........................ 1 The "Multi-Net".............................. 2 E-Mail....................................... 2 Multi-mail and CC:s.......................... 3 Networked File Listings...................... 3 Taglines..................................... 4 Joining VirtualNET........................... 5 NODE Request/Assignment Form................. 6 The Role of the AC........................... 7 Establishing a Client-Server connect......... 8 Network Decorum.............................. 9 Network Support.............................. 9 The Future................................... 10 Appendix A................................. 11 Installing the Net...................... 11 Requesting a net node................... 11 Automating the Network.................. 11 Xfer protocol options................... 11 Phone calling options................... 12 Appendix B................................. 13 VNET Command lines...................... 13 VNET Macros............................. 14 The Multi-Net........................... 15 The BBSLIST............................. 15 Appendix C.................................. 16 Deffinition of Subtypes................. 16 Procedures for Sub-Hosts................ 16 Setting Up Secured Subs................. 17 Handles/Real Names/Anon................. 18 Permanent Messages...................... 18 ────────────────────────────────────────────────────────── - 1 - -------------------- What is VirtualNET?: -------------------- VirtualNET is a wide area network of on-line bulletin board systems running the Virtual BBS software authored by Roland De Graaf. This fast growing network is free and open to all who wish to become a part of it. Friendly, fun, and non-political by nature, participation in VirtualNET is widely encouraged. Networked message areas, email, attached files to email, requestable networked filelistings, and gateways to other networks are a few of the features which highlight network activity. ------------------------ Networked Message Areas: ------------------------ At the core of VirtualNET are 22 message areas known as Star Message Bases. These are the original "non-hosted" VirtualNET subs, are a part of the "auto-request" group of sub types and carry a "*" designating them as such in the VirtualNET Subslist. Other Autorequest subs (topic areas) are available for automatic request by a SysOp and are listed in the current SUBSLIST.NET. To subscribe to these types of subs, all that needs to be done is to add them (including their sub # as a mesage base to your database.cfg). Aside from the Star Message Bases, listed (A) subs have informal "hosts". These hosts act as discussion leaders within a given message area and should be afforded some degree of courtesy in that regard. If a SysOp would like to "Host" a sub topic of his or her own, all that needs to be done is to contact the VirtualNET Subslist Coordinator 1@4080, provide a Formal Name for the sub with a brief description of it along with a request for a sub # assignment and inclusion into the next SUBSLiST.NET. The SUBSLIST is sent weekly to nodes which have been officialized in the BBSLIST. A *new type of sub capabilty has been added to the VNET ver 5.41 networking software which permits hosting subs that are by subsciption only. These secure (S) type subs require that to contact the sub-host formally with a request to receive a sub. The sub-host will generally then include you into the distribution of that sub and in some cases provide you with a synopsis of that sub and any rules that that sub-host may have regarding that message base. Each VirtualNET node is, at this time automatically assigned TWO (S)ecure type subs for use at his or her discretion. (see appendix C) Those sub numbers correspond to the node number and can be used for Local or national Message bases, networked file directories, or other networked databases. If a sysop wishes to make a sub available for national subscription, contacting the Subslist Coordinator would be prudent so that it could be shown as available in the national Subslist. All subs that are nationally available can be advertised in the #228 * "Yellow Pages" sub, which is also used for contacting the Subslist Coordinator regarding inclusion of (S) type subs and requests for sub # assignment of (A) Autorequest type subs from Sub-hosts. Generally, Autorequest subs are preferable for particularly new message subs because of their easy access to those who wish to 'tune in' and sample the sub as readers. ALL message or file subs which are "ADULT" in nature shall without exception, be (S) type subs. - 2 - ---------------- The "Multi-Net": ---------------- The Muli-Net is inclusive of other Networks and allows Message areas and email to be gated currently among VirtualNET, WWIVnet, and WWIVLink. In the very near future, the multinet will include gateways to Fido and QWK format networks. The multinet allows the "gating" of message bases and sub boards between networks. At the present time, Non hosted VirtualNET subs are themselves NOT being gated outside of the network. Hosted VirtualNET subs however may be gated as the "host" sees fit. To gate subs FROM other networks INTO VirtualNET, you must FIRST OBTAIN PERMISSION FROM THE HOST OF THAT SUB, and then request a Gateway sub type assignment from the VirtualNET Subslist Coordinator. To gate other networks between themselves, permission MUST be obtained from EACH sub or conference Host involved on those networks. SysOps who are found to NOT have secured the permission of a sub's host prior to making a gating request, or are otherwise providing a gateway into another network without permission of that network sub-host will have their listing dropped and find their future ability to obtain sub-assignments impaired. Gateway subs into other networks MUST conform to the rules and regulations of the network or network sub-host. VirtualNET nodes are not permitted to allow their gates to cause disruption within other networks. ------ Email: ------ Private email routing is a function of the network. Each user on your system has a unique VirtualNET address and if given appropriate security may send and recieve mail not only across VirtualNET but, also across the multinet (other networks). A user on any VirtualNET system may send email to a WWIVnet address for instance just by identifying the network name at the prompt after the user and node number (x@xxxx) is entered in the "To:" line. The mail is gated out to WWIVnet (or whatever network has been chosen) at the first "gate" it comes to as it is routed up the network. Conversely, a WWIVnet user may send mail to a VirtualNET user by directing it through a known email gateway. The main WWIV gateway routing address on VirtualNET is 2@6655. So, from a WWIVnet board, a WWIVnet user can send mail to a VirtualNET user like so; 1) address the mail to a WWIVnet gate 2@6655 (main VirtualNET gateway) 2) On the FIRST line of that email, address the person's VirtualNET address prefacing it with three "***". When the mail hits the gateway, the software will see that routing instruction and route the mail to the VirtualNET address. example: ***1@4080 Another Network feature of the email is attached files. Attached files may be sent to any address on VirtualNET by any user configured by the SysOp to do so. There is no limit on the size of the file which can be attached to an email. For that reason, you will probably want to limit the access of this feature. - 3 - ------------------- Multi-mail and CCs: ------------------- A unique and powerful feature of the VBBS/NET software is Multimail. This enables a SysOp and those with appropriate security levels as defined by the SysOp to maintain up to 9 seperate mailing lists, each with the ability to store an unlimited number of local and Network addresses which span the multinet. This INCLUDES the ability to CC: or multimail attached files this way as well. CC:s are seperately definable to user security and as multimail, there is no limit on the number of addresses that can be Carbon Copied at any given time. Note on Multimail Usage: VirtualNET considers itself a Guest of the networks within the Multinet. Each VirtualNET sysop has the responsibility to conduct themselves in a way which is becoming of that "guest" status. Arbitrary use of the CC or Multimail function is strongly discouraged. ------------------------ Networked File Listings: ------------------------ Along with Email and the Message Bases, VirtualNET features a the actual networking of FILES. Through an automated request system (functional but still in development), VirtualNET SysOps, by configuring their VBBS program to do so, may recieve File listings from networked directories across the network (see appendix for installation notes). These file listings appear on your system as downloadable files only, similar to <offline> listings, they are marked as <Network File>. By pressing "R", a user may reqest a networked file. The request is then sent to the SysOp for approval or disapproval. If approved, the request is then automatically sent to the SysOp of the originating board where that SysOp will A)pprove or D)issaprove the request. If the request is approved, the file is then sent. Once this system becomes polished, each VirtualNET board will be able to display File listings that may very well represent Hundreds and perhaps thousands of Megabytes of files on their system. - 4 - --------- Taglines: --------- Taglines are a great way to personalize posts, and appear as a stamp on the bottom of each posted message. There are two kinds of taglines in VBBS; Personal Taglines and System Tagines. Personal taglines are are optionally made available by the SysOp to the system users. If the option is made available, the user is provided up to 9 configurable taglines which are created in the user default area and are tagged onto posts by hitting ^C and then the tagline number (1-9). System taglines are made optional for each message base. Taglines are limited by the software and by VirtualNET policy to 3 lines of "Ascii" or "Heart code Ansi" color and to 300 bytes (characters). Tagline usage within VirtualNET itself is intended to maximize the informational value of the tagline. Each tagline, to comply with VirtualNET policy can include whatever information or extended Ascii (alt-XXX) characters a SysOp sees fit, but MUST contain the following information somewhere in the tagline; 1) BBS name 2) BBS Geographic location 3) VirtualNET node # 4) "VBBS" and version #. The three line tags can be created by using the SysOp EDIT function of VBBS's full screen editor or any other Ascii editor. Special ^P colors ('heart code ansi') can be used to colorize the tagline. There can be as many as 998 different system taglines. VBBS looks for your taglines in the directory which you have named in PATHS.CFG as your system TEXT directory. Taglines are created and saved as TAGLINE.1, TAGLINE.2, TAGLINE.3, etc all the way up to TAGLINE.998. TAGLINE.999 is special. By entering 990 to 999 into a database's tagline field, you tell the program to call your defined taglines at random. Naming 0 to the tagline field disables taglines altogether for that database. Taglines are a great thing and can be quite informative. SOME network sub hosts however, do not allow the use of taglines in their subs. If you carry "gated" subs or are part of another network, it is recommended that you familiarize yourself with policy related to tagline usage. - 5 - ------------------- Joining VirtualNET: ------------------- Note: VBBS/NET 5.41 installation is required before joining VirtualNET. Included with the VBBS 5.41 program, is a list of VirtualNET BBSs which is current at the time of the 5.41 release (BBSLIST.NET). If you would like to have your BBS join VirtualNET or have further questions regarding VirtualNET, please contact the Area Coordinator (AC) for your area as listed in the BBSLIST.NET. IF your area does not yet have an AC, please contact one of the VirtualNET Regional Coordinators (RC) as listed. All RCs can be reached through VirtualNET or WWIVnet addresses; Region 1 (Midwestern US) Minnesota, Iowa, Missouri, Wisconsin, Illinois, Kentucky, Indiana, Ohio, Michigan, North Dakota, South Dakota, Nebraska 218 612 507 712 515 319 816 417 314 715 906 414 608 815 708 309 217 618 312 502 606 812 317 219 419 216 513 614 616 517 313 605 701 308 402 --------------------------------- Region 2 (Eastern US) Virginia, W. Virginia, Maryland, Washington DC, Delaware, New Jersey, New York, Pennsylvania, Conneticut, Rhode Island, Maine, Vermont, New Hampshire 207 802 603 413 508 617 401 203 516 212 718 201 908 609 302 301 703 804 304 412 814 215 717 914 607 716 315 518 The Dutch Ghetto (Snoop) 1@6160 VirtualNET 1@6654 WWIVnet ---------------------------------- Region 3 (South US) Texas, North Carolina, South Carolina, Georgia, Tennessee, Arkansas, Louisiana, Mississippi, Alabama, Florida, Oklahoma 901 501 318 504 601 615 205 912 904 407 813 305 404 704 919 803 806 915 817 214 409 713 512 918 405 913 316 The Dragon's Den (Filo) 1@5120 VirtualNET 1@5252 WWIVnet ----------------------------------- Region 4 (Western US) Washington, Oregon, California, Montana, Idaho, Arizona, Nevada, New Mexico, Utah, Wyoming, Colorado, Alaska, Hawaii 307 801 303 719 702 602 505 406 208 714 310 408 209 805 619 916 707 415 818 213 510 808 206 509 503 809 907 The Lemurian Co-op (Cat In The Hat) 1@9160 VirtualNET 1@9699 WWIVnet ----------------------------------- Region 5 (Europe) The Transatlantic BBS (Neil J. Marshall) 1@440 VirtualNET 1@814 WWIVnet - 6 - There are many Area Coordinator positions not yet assigned and available. Should you desire to be the AC for your area, please let the RC know this in your node request email. Whether you are sending a node request to your AC or an RC, please use following format: Turning in a new node request: ----------------------- Block save this form ---------------------------- Board Name ________________ Sysop Name ________________ SysOp Date of birth _______ BBS Phone # (XXX)-XXX-XXXX Voice Phone# (XXX)-XXX-XXXX City, State, or Country _______________________ Max Baud Rate supported_________ Modem type (2400, /HST COMPUCOM, DS, V.32 etc..) Other Network affiliation (if any)____________________ -------- For AC use --------- Connect to: @xxxx (if known) Node # assigned ___________ Protocol (DSZ/HS-Link)______________ ----------------------- Block save this form ----------------------------- This is the standard form for a new VirtualNET node assignment. It gives the AC for your area the needed info to pass on to the Network RC. It also provides phone numbers to the network administration should there ever be a need to contact you. Once you have completed this form, please return it to your Area Coordinator or to a VirtualNET Regional Coordinator should your area not yet have an AC. --------------------------------------------- Node assignments are usually effected within a weeks time. Generally, you can expect to become official within a few weeks of your application. Updates to the BBSLIST.NET are sent out generally twice each week by the Regional Coordinators reflecting changes and additions made. - 7 - ------------------- The Role of the AC: ------------------- (ACs) - At the backbone of VirtualNET are the Area Coordinators. They are the ambassadors between their area and VirtualNET. Normally, one AC is assigned to each telephone area code. This position is purely voluntary. Area Coordinators are assigned by that region's RC. Requirements of the VirtualNET AC- 1) Be opperating an accessable VBBS 24 hours per day. 2) Be able and willing to provide time and effort toward support and the growth of the network. Duties of the VirtualNET ACs- 1) Promote and support VBBS/NET within your area as you are able. Encourage and help others to be a part of, and contributors to VirtualNET. 2) Provide a positive image of VirtualNET within the online community. 3) Resolve conflicts that arise when able within the area and promote harmonious participation within the network. 4) Active participation in the VirtualNET AC sub. By nature VirtualNET does NOT exclude anyone. There is NO basis for an arbitrary delay in providing a VBBS SysOp with particularly access to the VirtualNET support subs. New nodes that are in an area with an AC are expected to connect to the AC for at least one week prior to official node assignment so that they may sample and become better aclamated with the network and "iron out any wrinkles" in their installations. During this interim period, a pending SysOp may have access to networked message areas, but must have networked databases set to a 255SL access until such time that their node becomes official in the BBSLIST. VirtualNET is a FREE and OPEN network. It is non-exlusive by nature and is NOT hierarchal in the manner of many other networks. Often times, an AC might want to name an assistant AC to help particularly in the event that the AC is going to be inaccessable for any length of time. AC's are encouraged to provide at least one Area (S) type sub for use in discussing local issues and what not, making that sub available to all VirtualNET SysOps within his or her area. - 8 - -------------------------------------------- Establishing Connects (Servers and Clients): -------------------------------------------- A new VirtualNET node is asked to make an initial connect with that area's AC for at least one week and for as long as three weeks prior to the AC handing a node assignment in for addition to the international BBSLIST. The purpose of this is to ensure that the new node is fully familiar with the network and is setup properly before officially joining the network. This is particularly important in cases where that new node will be making an official connect directly with a national server. During this time of aclamation, pending node SysOps are allowed to have complete access to the VBBS/NET Support message bases and other message bases that are available. The SysOp is asked to maintain an SL setting of 255 on all network message bases until such time that his assignment has been reflected in an updated BBSLIST.NET. Normally, at the same time that a node number is assigned, a connect is established between the new node and a "Server". The stucture of the network is currently that of a "Hub". The main Server is located in Western Michigan using a US Robotics HST and the network branches out from that area. It is desirable for a node to make a local connect when possible. If there is currently more than one VirtualNET board in your area, consideration to become a "Client" of that system should be primary. Often, a local dialing area will name one system as the Server and divide the monthly networking costs by the number of BBSs in the local system. If there is not yet another VirtualNET BBS in your area, one of the two VirtualNET Regional Coordinators will help you in establishing the best connect for your board. Note: Once your Network account has been established, it is incumbant upon you as a Client to NET in to your Server in a timely manner. Due to matters regarding storage of Network Packets, Clients who do not NET in to their server for 3 days run the risk of having their pending packet deleted by the Server SysOp. If you are having problems, or for whatever reason are not able to recieve your packet from your Server on a timely basis, be sure to contact your Server right away. Also, if you are going to be leaving the network, please notify your Server as well as your Area Coordinator. -------------- The Subs List: -------------- The VirtualNET Subs List is updated weekly by the Subslist Coordinator. The current Subslist appears in your NET dir. All (A) subs are available to you by automated request. You simply need to add each sub you would like to recieve to your database.cfg. The subs come to you automatically and do not require that you request them from anyone. Once subscribing to a new sub however, it is common practice to announce your board's presence in that message area. Any questions regarding VirtualNET subs or Requests to either Host a VirtualNET sub or Gate a sub from another network need to be directed to the VirtualNET SUBSLiST Coordinator (1@4080 Friday Jones). The prefered method of requesting new subs is to post the request in the VirtualNET "Yellow Pages" sub. An acknoledgement of the request and a sub number assignment will follow from the Subslist Coordinator. There is no limitation on the number of subs a sysop may host nor limitation of the sub content other than "ADULT" subs are confined to (S) type message bases. Neither VirtualNET nor it's Network Coordinator endorse or maintain formal affiliation in any way to the subs hosted by the network sysops. Although VirtualNET maintains no responsibility to the activity of it's SysOps, illegal activity is expressly forbidden within the network. It is expected that VirtualNET SysOps will act in a responsible manner. Any networked BBS known to be engaging in activity which is not legal will be dropped from the Net list. - 9 - -------- Decorum: -------- VirtualNET was founded on the principle of common courtesy. In a sense, that is the only VirtualNET "rule". The network is place where information, ideas, and opinions all come together from different corners in a virtual cornucopia that celebrates the varied differences of backgrounds and experiences of those who are a part of the network. VirtualNET has been fortunate to date in not having to deal with an issue of a Network user creating problems for others. As we grow however, it is inevitable that a situation will arise which requires remedy. First and Foremost, it is a SysOp's unique responsibilty to limit Network access on his or her system to responsible users. SysOps are expected to handle any problem user which is accessing the network from his or her board. In the event that a problem is persistant, a warning will be issued to that system. If the problem continues, the Network Coordinator will have no choice other than to suspend the network connect to the originating node. -------- Support: -------- Sometimes things don't work quite as they should when first establishing a connect with a server. If you have read and followed the documentation, and find that you are for whatever reason recieving errors, contact your Server and let him or her know what the problem is. VBBS and VirtualNET share the same cooperative support structure. Servers, AC's and CORE support boards are there to help you should you experience problems. The posts that you send regarding problems should always include your Network address (node #), as well as your name, software version, WHICH network you're having problems with, and whether you are a running the program Standalone or as a door. It is important as well that you are as specific as possible regarding the nature of the problem as well as where it occurs. Invariably, almost all errors are the result of something not being quite right in the installation. The Support structure available to you is geared for maximum efficiency in resolving problems. No matter who you contact, your mail has a good chance of being forwarded within the support structure to another SysOp for resolution. This way, not only is the volume of support spread more evenly, but as well should result in a more prompt and accurate reply to the SysOp requiring support. As you have access to the VirtualNET Support Subs however, please make use of the public support by posting there whenever possible as it will provide the greatest benifit to the Net as a whole. There is a team of support SysOps affectionately known as the Virtual Ski Patrol. These volunteers are there to help resolve problems and questions which are posted and generally make sure that all posted problems and questions are resolved or answered. - 10 - ----------- The Future: ----------- The future of VirtualNET is heavily bound to the present. VirtualNET has the current distiction of being the fastest growing amateur network in the nation. With effort on the part of all pioneering VirtualNET SysOps, VirtualNET will continue to grow at an exponential rate. The future of the network software will see a continued efficiency of design. A utility now exists called VFIDO by Neil J. Marshall which will allow the inclusion of Fido format messages within VBBS. In the very near future, complete transparent capabilty will exist in VBBS for Fido. Registered VBBS SysOps who wish to be a part of beta testing VFIDO (now in version 2.0b), please contact Neil J. Marshall as VirtualNET 1@440 for more information. The continuing growth of the "Multi-net" will find more and more networks becoming a part of the great VBBS/NET internetworking experiment. The Networked Filelistings and request system can expect to see some polishing soon, to where the process will involve direct automated connects between Requesting and File listing VBBS boards which are a part of the file listing/request system. -= * =- - 11 - ----------- Appendix A: - N E T W O R K I N S T A L L A T I O N - ----------- In order to use the networking features, you will need to have the following programs: (Which VBBS will utilize automatically.) DSZ DSZ External Protocol Driver HS-LINK HS-Link Bi-directional Protocol (if desired) PKZIP and PKUNZIP PKware ZIP Archive Utilities Installing the Net- -------------------- The VirtualNET networking software, VNET.EXE is already included with the VBBS program. Once you have recieved you node assignment and have established yourself as a "client" to a VirtualNET "server" you simply need to do setup the NETWORK section in Vconfig. To do this, you enter your node number #### in the NETWORK.CFG. As well, you need to insert your Server node # and Phone #. Events and Dialing Thresholds ------------------------------- There are two ways to effect automation between Clients and servers. One way is to enable the dialing threshhold in network.cfg. Once the defined threshold of kb of pending messages is met, the software will either call your Server, or poll your clients (if any) depending on the situation. Local option is active 24 hours. Long Distance restricts the time of a particular network dialout to 12am and 8am. Threshold is disabled with a setting of 0. Another way to automate the network is to take advantage of one or more of VBBSs 20 definable events. See the VNET command lines that follow. Note that the switch directly follows VNET and does not require a <port> designator. These commands can be used from a DOS prompt as well as a batchfile and inserted as WFC function keys or as event batchfiles. Protocol Choices ---------------- VirtualNET SysOps have two choices in transfer protocol options. The default choice is Zmodem (DSZ) which is now a well established unidirectional standard. The other choice is the new and fast rising HS-Link which is a bi-directional and transfers both incoming and outgoing network packets at the same time. HS-Link can be a very efficient and cost effective method of xfer. It provides unidirectional throughput which is comparable to Zmodem, but is as of this writing, still in it's first release version and has not become as well established as Zmodem. If you choose to use HS-Link, it is important that the protocol is configured for both the client and the server. Clients will need to inform their server if they want to switch from one to another and coordinate a time that the change will be effected. Another important aspect of using HS-Link is that for MOST Network installations, the protocol comes properly configured. Do NOT use an HS-Link .CFG configuration file unless you have a specific need to do so. - 12 - Phone calling options --------------------- There are many phone calling options available to clients making long distance connects. AT&T, MCI and Sprint all have discount calling options for off peak calling and frequently called numbers. Contact those companies regarding the options available to you. Another popular calling option for some is a service known as PC Pursuit. For more information on PC Pursuit, contact the 800 information operator (1-800-555-1212) for the 800 PCP information desk in your area. The Main VirtualNET server in W. Michigan is NOT within an INDIAL PCP area. Other National VirtualNET servers ARE however and if you are using PCP, you will need to contact your RC regarding the establishment of a PCP connect. Below is an example of a PC Pursuit macro for VNET; {Delete the comments after the double slash (//)). Put your local PCP number in the network config in VCONFIG. Put this macro in your main VBBS directory and it should work just fine. ----------------Macro starts below this line---------------------------- SEND @D^M SEND D1^M RECV @ SEND D^M RECV NOT SEND C D/CASJO/24,IDxxxxxxxx,PWxxxx^M // Put your ID, PW and Server's // City code here RECV D/CASJO/24 CONNECTED // City code goes here also SEND I^M // Download the RVPrimer.arc SEND ATZ^M // from PC Pursuit or my BBS to RECV OK // understand why I did this SEND ^E^M // like this instead of using RECV HELLO // Hayes command set. SEND D7328958^M // Server's Phone Number goes here RECV ANSWER TONE // This line was included to delay the Vnet // 30 second time out feature. ---------------------End of Macro---------------------------------------- Please contact Lazurus Long (1@4081) for further assistance w/ PCP. - 13 - ----------- Appendix B: ----------- VNET 5.41 --------- VNET.EXE is the networking software for the Virtual BBS/NET. It should be run out of the same directory as your Virtual BBS. For the most part, VBBS.EXE activates VNET.EXE as needed, however there are command switches which you may employ during execution from a batchfile or Dos prompt. The syntax for VNET.EXE is: VNET <command-switch> <command-switch> tells VNET what to do, the possibilities are: /NET - This command does a network callout to your designated host. Upon completion, it exits back to DOS. /HOST - This option tells VNET.EXE that a VirtualNET system has called in, and that its time to do an "answering-system" net transfer. /DIAL# - This options lets a "Server" call to a "Client" system. (Sort of the reverse of /NET) # is the system to dial, as specified by CLIENT LIST POSITION. VNET /DIAL1 Would call the 1st system in your client list. /U - Updates all the mail packets. /A - Analyzes VirtualNET connect and bbslist information sent to you from the Network Coordinator. Example: VNET /A /$ #### - Used to List, review VirtualNET posts after bundling into Net Packets (similar to LNET in WWIVnet) #### is PKT####.NET file to examine. - 14 - ------------ VNET Macros: ------------ VBBS has the unique ability of Vnet.exe to employ the use of macros in establishing a Net connection with another VBBS system. If you are running VBBS from a matrix logon or as a door within another system, you now have the ability to serve as a VirtualNET HOST system to other boards from WITHIN the matrix logon or BBS door. If you are already the host to a remote VirtualNET system which is running in a matrix logon or door, you may now connect to that system for polling or whatever. The macro supports 3 commands. All 3 commands are 4 characters long, and 1 space is expected between the command and its arguement. RECV Waits for a string of characters. If they don't show up within 30 seconds, the call is aborted. SEND Sends a string of characters. WAIT Tells the macro facility what the boards [PAUSE] string is, so that it can be handled should it come up when RECV is waiting for its string. If it pops up, the macro facility automatically sends a 0x0D. The use of this facility is optional. A WWIV example: WAIT [PAUSE] RECV NN: SEND Acct name^m RECV PW: SEND codeword^m RECV ###-###- SEND 0000^m RECV T - SEND . RECV ? SEND 1 The above example logs on to a WWIV board, and runs door # 1. Note that you may send and recv control characters by putting a ^ in front of them. When the macro is done executing, VNET.EXE proceeds immediately to waiting for the ° which should pop up when VBBS starts running as a door. - 15 - The Multi-net VBBS, along with VirtualNET is currently able to directly access WWIVnet and/or WWIVLink and run all three networks at one time transparently with each other. Registered SysOps will be given the VWW4.EXE which will enable the FULL use of the WWIVnet and/or WWIVLink networking software alongside of VirtualNET from within VBBS. A particularly notable feature of running WWIVnet inside of VBBS is that VBBS is able to carry an UNLIMITED number of Network subs. VBBS can even act as a WWIVnet SERVER! VirtualNET is a gateway to WWIVnet and WWIVLink. That is each VBBS/VirtualNET user has the unique ability to access WWIVnet mail, as well as any gated subs being carried by your board. In order to gate a WWIVnet or WWIVLink sub into VirtualNET, you simply need to assign it a VirtualNET networked sub number in addition to it's WWIVnet or WWIVLink sub type. (Please see the VWW4SYS.DOC documentation by UT Prof 1@5121) VBBS will soon be adding additional networks into the "Multinet" including QWK format Networks. A Fidonet interface, VFIDO 2.0 by Neil J. Marshall is currently in beta stage and seeking beta testers (contact 1@440 VirtualNET for details). In the near future, Full Fido transparency will exist within the Multinet. The BBSLIST.NET --------------- A master list of VirtualNET nodes exists as BBSLIST.NET and is located in each board's NET directory. If for some reason you do not have a BBSLIST in your 5.4X NET dir then you will need to obtain the most current version from your AC or another VirtualNET board. You will always want to start with the most current BBSLIST.NET available. Updates to the BBSLIST.NET update the changes only and the entire BBSLIST.NET is not sent with the updates. A new node will need to insert the most current BBSLIST.NET into the NET dir and run VNET /A from the main VBBS dir to analyze the list so that it is readable by VBBS. Network updates are usually sent twice each week by the Regional Coordinators. If your new node is not being reflected in an updated BBSLIST.NET as expected, contact your Area Coordinator. - 16 - ----------- Appendix C: ----------- Definition of Sub types: ------------------------ There are 3 basic network Sub types; (P) Private Messages such as EMAIL, (A) Autorequest type subs which are received by simply entering them in database.cfg, (S) Secure subs which require that you contact the sub-host of that networked area regarding being put on the distribution list. The (A) and (S) type subs are broken down by VNET into two groups of integers as shown below. The allocation of the (S) type subs is also defined here: (A) Autorequest subs are numbered from 1 to 10000. This subtype may be used for any sub which is not "adult" in nature or is otherwise restrictive. (S) Secure subs are numbered from 10001 to 59999. Each VirtualNET node is assigned FIVE discetionary secure subs for their hosted use. A VirtualNET node @5090 would receive sub numbers 15090, 25090, 35090, 45090, and 55090. If a SysOp requires further Secure sub assignments, other integers above 59999 are available by special request from the Network Coordinator 1@1. Procedures for Sub-Hosts ------------------------ When you have a message base or other networked area which you would like to "Host", you will need to first decide what type of sub you would like it to be. The (S) secure type subs are generally preferable as they are more efficient relative to their routing. Autorequest type subs can be desirable for new subs as it provides the easist access to them and can give a sub-host a good idea how much interest there is in maintaining that networked sub. ALL Local type subs, that is those which are national/international in nature, as well as ALL "adult" content type subs MUST be (S) secure subs according to VirtualNET Policy. Subs which are gated into other networks will always follow the rules of that network. Sub-hosts of GATED subs shall respect the rules and policies of the originating network's sub host (if any) and insure that gateway subscribers follow the wishes of that network's sub host. It is reccomended that GATED subs use the (S) secure sub types. Once you have a networked area that you would like to host, you will need to give it a formal name and a description for the Subslist Coordinator. If you are hosting a (S) secure sub, you will need to post the name and description of the sub, along with the sub-host VirtualNET address and the subtype so that it may be recorded in the SUBSLIST.NET. If your new network sub is an (A) autorequest sub, then you will additionally post a REQUEST to the Subslist Coordinator (1@4080 Friday Jones) for an sub number assignment there on the Yellow Pages sub #228. The Yellow pages sub should also be used for advertizing your sub (ansi art allowed). - 17 - Setting Up Secured Subs: V#####.NET and VV#####.NET files ---------------------------------------------------------- V#####.NET and VV#####.NET files (##### = sub number) are text files that reside in your VBBS network directory. V#####.NET files are used by sub hosts to set up their list of subscribers. It is just a simple text file, with one entry per line. The entries are the node numbers of the subscribers. VV#####.NET files are used by subscribing systems to identify the sub host. There is only one entry in a VV#####.NEt file -- the node number of the sub host. If you would like to HOST a secured sub: 1. Determine what sub number you want to use. (See pg 16 for more info on sub numbering.) 2. Create the sub database -- dont forget the sub number! 3. Advertise on the Yellow Pages, give the sub number, the sub name, a brief description, and the node address of the host of the sub. 4. As requests for a sub pour in, enter the node numbers, one per line, into a V#####.NET file, as ascii text. ##### = sub number. If you would like to SUBSCRIBE to a sub: 1. Email the Host of the sub asking for access Be sure to specify the sub number. 2. Create a VV#####.NET file containing one line, the node number of the sub host. ##### = sub number. 3. Create a new database for the sub -- dont forget the sub number! - 18 - Handles/Real Names/Anonymous ---------------------------- In the database.cfg, the SysOp has the ability to toggle usage of Handles, Real names or anonymous posting. All subs will be assumed to be handles unless the sub-host designates otherwise to the Subslist Coordinator. Real names are often required in other networks and if a GATED sub requires Real names then the VirtualNET host is responsible for that being made known to the Subslist Coordinator. Anonymous posts can be useful for instance in support and recovery type of message bases where a sub-host feels that users would be more comfortable obscuring their identity altogether. Permanent Messages ------------------ Permanent messages are a great way for a SysOp to display in a message base, a synopsis and any rules regarding that message base. Sub Hosts may decide from time to time post a message base specific permanent message for the subscribing SysOps to flag for a permanent post. When that post reaches the # 1 position, it will not be purged. This way, an explaination of the message base can always be found in the first post of a message base. EOF -=-=-=-=-=-=-=-=-=-=-=- VirtualNET Guide ver 5.42 compiled by 1@9160